Summary

Fixes an infinite loop in paginate() (issue #35) where the CLI hangs indefinitely when a filtered list endpoint returns { items: [], nextToken: 'cursor' }.

Problem

paginate() in src/lib/pagination.ts checked nextToken !== null to decide whether to keep looping, but never checked whether items was actually empty. Without --max-items set, the loop had no way to stop for this edge case, causing testsprite test list --project <id> with a zero-result filter to hang forever.

Fix

Added an early-exit guard after processing each page:

// Guard against infinite loop when API returns empty items with non-null nextToken.
if (page.items.length === 0) break;

This breaks the loop when the API returns zero items, regardless of what nextToken says. The nextToken from the server is still returned to the caller for potential resume.

Changes

• src/lib/pagination.ts: Added empty-items guard in paginate() loop
• test/pagination.test.ts: New file with 5 unit tests:
  • Collects all items across pages until nextToken is null
  • Breaks out of loop on empty items with non-null nextToken (the bug repro)
  • Respects maxItems cap
  • Handles single page with null nextToken
  • Handles consecutive empty pages then data

Testing

• npm run typecheck — clean
• npm run lint — clean
• npm run format:check — all files pass Prettier
• npm test — all existing tests + 5 new tests pass

Closes #35

Signed-off-by: Aldo Rizona aldorizona10@gmail.com